Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Checks
Changes
Remove
pnpmfield fromenginesin package.jsonContext
During dependency installation in my project using Yarn, I noticed the following message:
The
pnpmentry inengineswas introduced in #966, which migrated from npm to pnpm. The same PR also correctly setspackageManagertopnpm- That's the important field used when developing eslint-plugin-testing-library itself.There is no reason to require consumers of
eslint-plugin-testing-libraryto use pnpm (or any specific package manager). Therefore, the best solution is to simply remove the entry fromenginesaltogether.